Reporting transmission for discontinuous reception

ABSTRACT

Apparatuses, methods, and systems are disclosed for reporting transmission for discontinuous reception. One method includes determining whether a symbol occurs within a discontinuous reception on duration time period. The method includes, in response to determining that the symbol occurs within the discontinuous reception on duration time period, determining whether to transmit a report. The method includes transmitting the report regardless of whether a discontinuous reception on duration timer is running.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Patent Application Ser. No.62/899,370 entitled “APPARATUSES, METHODS, AND SYSTEMS FOR A DRXOPERATION CONSIDERING WAKE-UP SIGNALING” and filed on Sep. 12, 2019 forJoachim Loehr, which is incorporated herein by reference in itsentirety.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to reporting transmissionfor discontinuous reception.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description: Third GenerationPartnership Project (“3GPP”), 5^(th) Generation (“5G”), QoS for NR V2XCommunication (“5QI/PQI”), Authentication, Authorization, and Accounting(“AAA”), Positive-Acknowledgment (“ACK”), Application Function (“AF”),Authentication and Key Agreement (“AKA”), Aggregation Level (“AL”),Access and Mobility Management Function (“AMF”), Angle of Arrival(“AoA”), Angle of Departure (“AoD”), Access Point (“AP”), ApplicationServer (“AS”), Application Service Provider (“ASP”), Autonomous Uplink(“AUL”), Authentication Server Function (“AUSF”), Authentication Token(“AUTN”), Background Data (“BD”), Background Data Transfer (“BDT”), BeamFailure Detection (“BFD”), Beam Failure Recovery (“BFR”), Binary PhaseShift Keying (“BPSK”), Base Station (“BS”), Buffer Status Report(“BSR”), Bandwidth (“BW”), Bandwidth Part (“BWP”), Cell RNTI (“C-RNTI”),Carrier Aggregation (“CA”), Channel Access Priority Class (“CAPC”),Contention-Based Random Access (“CBRA”), Clear Channel Assessment(“CCA”), Common Control Channel (“CCCH”), Control Channel Element(“CCE”), Cyclic Delay Diversity (“CDD”), Code Division Multiple Access(“CDMA”), Control Element (“CE”), Contention-Free Random Access(“CFRA”), Configured Grant (“CG”), Closed-Loop (“CL”), CoordinatedMultipoint (“CoMP”), Channel Occupancy Time (“COT”), Cyclic Prefix(“CP”), Cyclical Redundancy Check (“CRC”), Configured Scheduling RNTI(“CS-RNTI”), Channel State Information (“CSI”), Channel StateInformation-Reference Signal (“CSI-RS”), Common Search Space (“CSS”),Control Resource Set (“CORESET”), Dual Connectivity (“DC”), DiscreteFourier Transform Spread (“DFTS”), Downlink Control Information (“DCI”),Downlink Feedback Information (“DFI”), Downlink (“DL”), DemodulationReference Signal (“DMRS”), Data Network Name (“DNN”), Data Radio Bearer(“DRB”), Discontinuous Reception (“DRX”), Dedicated Short-RangeCommunications (“DSRC”), Downlink Pilot Time Slot (“DwPTS”), EnhancedClear Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”),Evolved Node B (“eNB”), Extensible Authentication Protocol (“EAP”),Effective Isotropic Radiated Power (“EIRP”), European TelecommunicationsStandards Institute (“ETSI”), Frame Based Equipment (“FBE”), FrequencyDivision Duplex (“FDD”), Frequency Division Multiplexing (“FDM”),Frequency Division Multiple Access (“FDMA”), Frequency DivisionOrthogonal Cover Code (“FD-OCC”), Frequency Range 1—sub 6 GHz frequencybands and/or 410 MHz to 7125 MHz (“FR1”), Frequency Range 2—24.25 GHz to52.6 GHz (“FR2”), Universal Geographical Area Description (“GAD”),Guaranteed Bit Rate (“GBR”), Group Leader (“GL”), 5G Node B or NextGeneration Node B (“gNB”), Global Navigation Satellite System (“GNSS”),General Packet Radio Services (“GPRS”), Guard Period (“GP”), GlobalPositioning System (“GPS”), General Public Subscription Identifier(“GPSI”), Global System for Mobile Communications (“GSM”), GloballyUnique Temporary UE Identifier (“GUTI”), Home AMF (“hAMF”), HybridAutomatic Repeat Request (“HARQ”), Home Location Register (“HLR”),Handover (“HO”), Home PLMN (“HPLMN”), Home Subscriber Server (“HSS”),Hash Expected Response (“HXRES”), Identity or Identifier (“ID”),Information Element (“IE”), International Mobile Equipment Identity(“IMEI”), International Mobile Subscriber Identity (“IMSI”),International Mobile Telecommunications (“IMT”), Internet-of-Things(“IoT”), Interruption RNTI (“INT-RNTI”), Key Management Function(“KMF”), Layer 1 (“L1”), Layer 2 (“L2”), Layer 3 (“L3”), LicensedAssisted Access (“LAA”), Local Area Data Network (“LADN”), Local AreaNetwork (“LAN”), Load Based Equipment (“LBE”), Listen-Before-Talk(“LBT”), Logical Channel (“LCH”), Logical Channel Group (“LCG”), LogicalChannel Prioritization (“LCP”), Log-Likelihood Ratio (“LLR”), Long TermEvolution (“LTE”), Multiple Access (“MA”), Medium Access Control(“MAC”), Multimedia Broadcast Multicast Services (“MBMS”), Maximum BitRate (“MBR”), Master Cell Group (“MCG”), Minimum Communication Range(“MCR”), Modulation Coding Scheme (“MCS”), Master Information Block(“MIB”), Multimedia Internet Keying (“MIKEY”), Multiple Input MultipleOutput (“MIMO”), Mobility Management (“MM”), Mobility Management Entity(“MME”), Mobile Network Operator (“MNO”), Mobile Originated (“MO”),massive MTC (“mMTC”), Maximum Power Reduction (“MPR”), Machine TypeCommunication (“MTC”), Multi User Shared Access (“MUSA”), Non AccessStratum (“NAS”), Narrowband (“NB”), Negative-Acknowledgment (“NACK”) or(“NAK”), New Data Indicator (“NDP”), Network Entity (“NE”), NetworkExposure Function (“NEF”), Network Function (“NF”), Next Generation(“NG”), NG 5G S-TMSI (“NG-5G-S-TMSI”), Non-Orthogonal Multiple Access(“NOMA”), New Radio (“NR”), NR Unlicensed (“NR-U”), Network RepositoryFunction (“NRF”), Network Scheduled Mode (“NS Mode”) (e.g., networkscheduled mode of V2X communication resource allocation—Mode-1 in NR V2Xand Mode-3 in LTE V2X), Network Slice Instance (“NSI”), Network SliceSelection Assistance Information (“NSSAI”), Network Slice SelectionFunction (“NSSF”), Network Slice Selection Policy (“NSSP”), Operation,Administration, and Maintenance System or Operation and MaintenanceCenter (“OAM”), Orthogonal Frequency Division Multiplexing (“OFDM”),Open-Loop (“OL”), Other System Information (“OSI”), Power AngularSpectrum (“PAS”), Physical Broadcast Channel (“PBCH”), Power Control(“PC”), UE to UE interface (“PC5”), Policy and Charging Control (“PCC”),Primary Cell (“PCell”), Policy Control Function (“PCF”), Physical CellIdentity (“PCP”), Physical Downlink Control Channel (“PDCCH”), PacketData Convergence Protocol (“PDCP”), Packet Data Network Gateway (“PGW”),Physical Downlink Shared Channel (“PDSCH”), Pattern Division MultipleAccess (“PDMA”), Packet Data Unit (“PDU”), Physical Hybrid ARQ IndicatorChannel (“PHICH”), Power Headroom (“PH”), Power Headroom Report (“PHR”),Physical Layer (“PHY”), Public Land Mobile Network (“PLMN”), PC5 QoSClass Identifier (“PQI”), Physical Random Access Channel (“PRACH”),Physical Resource Block (“PRB”), Proximity Services (“ProSe”),Positioning Reference Signal (“PRS”), Physical Sidelink Control Channel(“PSCCH”), Primary Secondary Cell (“PSCell”), Physical Sidelink FeedbackControl Channel (“PSFCH”), Physical Uplink Control Channel (“PUCCH”),Physical Uplink Shared Channel (“PUSCH”), QoS Class Identifier (“QCI”),Quasi Co-Located (“QCL”), Quality of Service (“QoS”), Quadrature PhaseShift Keying (“QPSK”), Registration Area (“RA”), RA RNTI (“RA-RNTI”),Radio Access Network (“RAN”), Random (“RAND”), Radio Access Technology(“RAT”), Serving RAT (“RAT-1”) (serving with respect to Uu), Other RAT(“RAT-2”) (non-serving with respect to Uu), Random Access Procedure(“RACH”), Random Access Preamble Identifier (“RAPID”), Random AccessResponse (“RAR”), Resource Block Assignment (“RBA”), Resource ElementGroup (“REG”), Radio Link Control (“RLC”), RLC Acknowledged Mode(“RLC-AM”), RLC Unacknowledged Mode/Transparent Mode (“RLC-UM/TM”),Radio Link Failure (“RLF”), Radio Link Monitoring (“RLM”), Radio NetworkTemporary Identifier (“RNTI”), Reference Signal (“RS”), RemainingMinimum System Information (“RMSI”), Radio Resource Control (“RRC”),Radio Resource Management (“RRM”), Resource Spread Multiple Access(“RSMA”), Reference Signal Received Power (“RSRP”), Received SignalStrength Indicator (“RSSI”), Round Trip Time (“RTT”), Receive (“RX”),Sparse Code Multiple Access (“SCMA”), Scheduling Request (“SR”),Sounding Reference Signal (“SRS”), Single Carrier Frequency DivisionMultiple Access (“SC-FDMA”), Secondary Cell (“SCell”), Secondary CellGroup (“SCG”), Shared Channel (“SCH”), Sidelink Control Information(“SCI”), Sub-carrier Spacing (“SCS”), Service Data Unit (“SDU”),Security Anchor Function (“SEAF”), Sidelink Feedback Content Information(“SFCI”), Slot Format Indication RNTI (“SFI-RNTI”), Serving Gateway(“SGW”), System Information Block (“SIB”), SystemInformationBlockType1(“SIB1”), SystemInformationBlockType2 (“SIB2”), SubscriberIdentity/Identification Module (“SIM”),Signal-to-Interference-Plus-Noise Ratio (“SINR”), Sidelink (“SL”),Service Level Agreement (“SLA”), Sidelink Synchronization Signals(“SLSS”), Session Management (“SM”), Session Management Function(“SMF”), Semi-Persistent (“SP”), Special Cell (“SpCell”), Single NetworkSlice Selection Assistance Information (“S-NSSAI”), Scheduling Request(“SR”), Signaling Radio Bearer (“SRB”), Sounding Reference Signal(“SRS”), Shortened TMSI (“S-TMSI”), Shortened TTI (“sTTI”),Synchronization Signal (“SS”), Sidelink CSI RS (“S-CSI RS”), SidelinkPRS (“S-PRS”), Sidelink SSB (“S-SSB”), Synchronization Signal Block(“SSB”), Subscription Concealed Identifier (“SUCI”), Scheduling UserEquipment (“SUE”), Supplementary Uplink (“SUL”), Subscriber PermanentIdentifier (“SUPI”), Tracking Area (“TA”), TA Identifier (“TM”), TAUpdate (“TAU”), Timing Alignment Timer (“TAT”), Transport Block (“TB”),Transport Block Size (“TBS”), Time-Division Duplex (“TDD”), TimeDivision Multiplex (“TDM”), Time Division Orthogonal Cover Code(“TD-OCC”), Temporary Mobile Subscriber Identity (“TMSI”), Time ofFlight (“ToF”), Transmission Power Control (“TPC”), TransmissionReception Point (“TRP”), Transmission Time Interval (“TTI”), Transmit(“TX”), Uplink Control Information (“UCI”), Unified Data ManagementFunction (“UDM”), Unified Data Repository (“UDR”), User Entity/Equipment(Mobile Terminal) (“UE”) (e.g., a V2X UE), UE Autonomous Mode (UEautonomous selection of V2X communication resource—e.g., Mode-2 in NRV2X and Mode-4 in LTE V2X. UE autonomous selection may or may not bebased on a resource sensing operation), Uplink (“UL”), UL SCH(“UL-SCH”), Universal Mobile Telecommunications System (“UMTS”), UserPlane (“UP”), UP Function (“UPF”), Uplink Pilot Time Slot (“UpPTS”),Ultra-reliability and Low-latency Communications (“URLLC”), UE RouteSelection Policy (“URSP”), Vehicle-to-Vehicle (“V2V”),Vehicle-to-Anything (“V2X”), V2X UE (e.g., a UE capable of vehicularcommunication using 3GPP protocols), Visiting AMF (“vAMF”), V2XEncryption Key (“VEK”), V2X Group Key (“VGK”), V2X MIKEY Key (“VMK”),Visiting NSSF (“vNSSF”), Visiting PLMN (“VPLMN”), V2X Traffic Key(“VTK”), Wide Area Network (“WAN”), Worldwide Interoperability forMicrowave Access (“WiMAX”), and Wake-Up Signaling or Wake-Up Signals(“WUS”).

In certain wireless communications networks, discontinuous reception mayoccur.

BRIEF SUMMARY

Methods for reporting transmission for discontinuous reception aredisclosed. Apparatuses and systems also perform the functions of themethods. One embodiment of a method includes determining whether asymbol occurs within a discontinuous reception on duration time period.In some embodiments, the method includes, in response to determiningthat the symbol occurs within the discontinuous reception on durationtime period, determining whether to transmit a report. In certainembodiments, the method includes transmitting the report regardless ofwhether a discontinuous reception on duration timer is running.

One apparatus for reporting transmission for discontinuous receptionincludes a processor that: determines whether a symbol occurs within adiscontinuous reception on duration time period; and, in response todetermining that the symbol occurs within the discontinuous reception onduration time period, determines whether to transmit a report. Invarious embodiments, the apparatus includes a transmitter that transmitsthe report regardless of whether a discontinuous reception on durationtimer is running.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for reporting transmission fordiscontinuous reception;

FIG. 2 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for reporting transmission for discontinuousreception;

FIG. 3 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for reporting transmission for discontinuousreception;

FIG. 4 is a timing diagram illustrating one embodiment of a DRX cycle;and

FIG. 5 is a flow chart diagram illustrating one embodiment of a methodfor reporting transmission for discontinuous reception.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,embodiments may take the form of a program product embodied in one ormore computer readable storage devices storing machine readable code,computer readable code, and/or program code, referred hereafter as code.The storage devices may be tangible, non-transitory, and/ornon-transmission. The storage devices may not embody signals. In acertain embodiment, the storage devices only employ signals foraccessing code.

Certain of the functional units described in this specification may belabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom very-large-scale integration(“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such aslogic chips, transistors, or other discrete components. A module mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices or the like.

Modules may also be implemented in code and/or software for execution byvarious types of processors. An identified module of code may, forinstance, include one or more physical or logical blocks of executablecode which may, for instance, be organized as an object, procedure, orfunction. Nevertheless, the executables of an identified module need notbe physically located together, but may include disparate instructionsstored in different locations which, when joined logically together,include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different computer readable storage devices.Where a module or portions of a module are implemented in software, thesoftware portions are stored on one or more computer readable storagedevices.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. The code may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

FIG. 1 depicts an embodiment of a wireless communication system 100 forreporting transmission for discontinuous reception. In one embodiment,the wireless communication system 100 includes remote units 102 andnetwork units 104. Even though a specific number of remote units 102 andnetwork units 104 are depicted in FIG. 1 , one of skill in the art willrecognize that any number of remote units 102 and network units 104 maybe included in the wireless communication system 100.

In one embodiment, the remote units 102 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), aerialvehicles, drones, or the like. In some embodiments, the remote units 102include wearable devices, such as smart watches, fitness bands, opticalhead-mounted displays, or the like. Moreover, the remote units 102 maybe referred to as subscriber units, mobiles, mobile stations, users,terminals, mobile terminals, fixed terminals, subscriber stations, UE,user terminals, a device, or by other terminology used in the art. Theremote units 102 may communicate directly with one or more of thenetwork units 104 via UL communication signals. In certain embodiments,the remote units 102 may communicate directly with other remote units102 via sidelink communication.

The network units 104 may be distributed over a geographic region. Incertain embodiments, a network unit 104 may also be referred to as anaccess point, an access terminal, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, a device, a core network, anaerial server, a radio access node, an AP, NR, a network entity, an AMF,a UDM, a UDR, a UDM/UDR, a PCF, a RAN, an NSSF, an AS, an NEF, a keymanagement server, a KMF, or by any other terminology used in the art.The network units 104 are generally part of a radio access network thatincludes one or more controllers communicably coupled to one or morecorresponding network units 104. The radio access network is generallycommunicably coupled to one or more core networks, which may be coupledto other networks, like the Internet and public switched telephonenetworks, among other networks. These and other elements of radio accessand core networks are not illustrated but are well known generally bythose having ordinary skill in the art.

In one implementation, the wireless communication system 100 iscompliant with NR protocols standardized in 3GPP, wherein the networkunit 104 transmits using an OFDM modulation scheme on the DL and theremote units 102 transmit on the UL using a SC-FDMA scheme or an OFDMscheme. More generally, however, the wireless communication system 100may implement some other open or proprietary communication protocol, forexample, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants,CDMA2000, Bluetooth®, ZigBee, Sigfoxx, among other protocols. Thepresent disclosure is not intended to be limited to the implementationof any particular wireless communication system architecture orprotocol.

The network units 104 may serve a number of remote units 102 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The network units 104 transmit DL communicationsignals to serve the remote units 102 in the time, frequency, and/orspatial domain.

In various embodiments, a remote unit 102 may determine whether a symboloccurs within a discontinuous reception on duration time period. In someembodiments, the remote unit 102 may, in response to determining thatthe symbol occurs within the discontinuous reception on duration timeperiod, determine whether to transmit a report. In certain embodiments,the method includes transmitting the report regardless of whether adiscontinuous reception on duration timer is running. Accordingly, theremote unit 102 may be used for reporting transmission for discontinuousreception.

FIG. 2 depicts one embodiment of an apparatus 200 that may be used forreporting transmission for discontinuous reception. The apparatus 200includes one embodiment of the remote unit 102. Furthermore, the remoteunit 102 may include a processor 202, a memory 204, an input device 206,a display 208, a transmitter 210, and a receiver 212. In someembodiments, the input device 206 and the display 208 are combined intoa single device, such as a touchscreen. In certain embodiments, theremote unit 102 may not include any input device 206 and/or display 208.In various embodiments, the remote unit 102 may include one or more ofthe processor 202, the memory 204, the transmitter 210, and the receiver212, and may not include the input device 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 202 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 202 executes instructions stored in thememory 204 to perform the methods and routines described herein. Theprocessor 202 is communicatively coupled to the memory 204, the inputdevice 206, the display 208, the transmitter 210, and the receiver 212.

The memory 204, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 204 includes volatile computerstorage media. For example, the memory 204 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 204 includes non-volatilecomputer storage media. For example, the memory 204 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 204 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 204 also stores program code and related data, such as anoperating system or other controller algorithms operating on the remoteunit 102.

The input device 206, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 206 maybe integrated with the display 208, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device206 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 206 includes two ormore different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronicallycontrollable display or display device. The display 208 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 208 includes an electronic display capable of outputtingvisual data to a user. For example, the display 208 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display208 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 208 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakersfor producing sound. For example, the display 208 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 208 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 208 may be integrated with the input device206. For example, the input device 206 and display 208 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 208 may be located near the input device 206.

In certain embodiments, the processor 202 may: determine whether asymbol occurs within a discontinuous reception on duration time period;and, in response to determining that the symbol occurs within thediscontinuous reception on duration time period, determine whether totransmit a report. In some embodiments, the transmitter 210 may transmitthe report regardless of whether a discontinuous reception on durationtimer is running.

Although only one transmitter 210 and one receiver 212 are illustrated,the remote unit 102 may have any suitable number of transmitters 210 andreceivers 212. The transmitter 210 and the receiver 212 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 210 and the receiver 212 may be part of a transceiver.

FIG. 3 depicts one embodiment of an apparatus 300 that may be used forreporting transmission for discontinuous reception. The apparatus 300includes one embodiment of the network unit 104. Furthermore, thenetwork unit 104 may include a processor 302, a memory 304, an inputdevice 306, a display 308, a transmitter 310, and a receiver 312. As maybe appreciated, the processor 302, the memory 304, the input device 306,the display 308, the transmitter 310, and the receiver 312 may besubstantially similar to the processor 202, the memory 204, the inputdevice 206, the display 208, the transmitter 210, and the receiver 212of the remote unit 102, respectively.

In certain embodiments, the transmitter 310 may be used for transmittinginformation described herein and/or the receiver 312 may be used forreceiving information described herein.

In various embodiments, there may be power saving techniques used toenhance UE battery lifetime. As may be appreciated, a UE battery lifemay be an important aspect of a user's experience and may influenceadoption of 5G handsets and/or services. In some embodiments, DRXoperation and/or BWP adaptation may provide UE power saving in NRoperation.

In certain embodiments, a power saving technique used may be WUS thatadapts a DRX active time of a UE based on some wake-up signal and/orchannel. In such embodiments, the UE monitors at a preconfiguredoccasion (e.g., WUS-occasion) for a new signal and/or channel (e.g.,PDCCH-WUS) that indicates whether the UE shall wake-up to monitor PDCCHduring a next occurrence of a timer (e.g., DRX-onDurationTimer). If thenew signal and/or channel (e.g., PDCCH-WUS) indicates to the UE towake-up to monitor the PDCCH during the next occurrence of the timer(e.g., DRX-onDurationTimer), the UE starts the timer at its nextdrx-onDurationTimer duration occasion, otherwise the UE does not startthe timer at its next occasion.

In one embodiment, at a WUS occasion during a DRX inactive time, a UEmay enter a first stage for monitoring a wake-up PDCCH (e.g.,PDCCH-WUS). At this stage, a UE's capability for power saving may bestrictly limited. For example, the UE may not expect to receive asame-slot scheduling grant for PDSCH or to be ready to transmit PUCCH inresponse to the PDSCH reception. Moreover, once the UE decodes a wake-upPDCCH in the WUS occasion, there may be a time offset for a nextonDuration. Therefore, in the first stage, a lower power implementationmay be achieved by optimizing, at least: (i) a PDCCH processingtimeline; (ii) an amount of hardware needed to be online; (iii) avoltage and/or clock operating point of hardware; and/or (iv) an RXbandwidth and a number of antennas. If a PDCCH-WUS is decoded indicatingfor the UE to wake up at the next onDuration, the UE may transition to asecond stage by waking up additional hardware and processing to getready for DL and/or UL data scheduling.

In various embodiments: 1) a PDCCH-WUS triggers a MAC entity to “wakeup” to monitor PDCCH at a reception of a PDCCH-based power saving signaland/or channel for a next occurrence of a drx-onDurationTimer duration;2) the PDCCH-WUS is considered jointly with DRX (e.g., it is onlyconfigured if DRX is configured); 3) the PDCCH-WUS is monitored atoccasions located at a configured offset before the start of thedrx-onDurationTimer—the offset is part of a physical layer design; 4) ona PDCCH-WUS occasion that a UE is monitoring, if the UE is indicated towake-up to monitor the PDCCH during the next occurrence of thedrx-onDurationTimer duration, the UE starts the drx-onDurationTimer atits next occasion—otherwise it does not; 5) the UE does not monitor WUSduring active time; 6) if the UE is in a DRX active time during aPDCCH-WUS occasion, it starts the drx-onDurationTimer at its nextOnduration occasion; 7) the WUS is configured on a PCell with CA andSpCell with DC (e.g., PCell on MCG and PSCell on SCG); and/or 8) RLM andRRM measurements are not impacted by WUS design (i.e. the UE continuesto measure the required reference signals as per RRM requirements).

In certain embodiments, to provide reasonable battery consumption ofuser equipment, DRX may have enhancements to handle differentnumerologies.

In various embodiments, a MAC entity may be configured by RRC with a DRXfunctionality that controls a UE's PDCCH monitoring activity for the MACentity's C-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI,TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, and/or TPC-SRS-RNTI. In certainembodiments, a common DRX scheme may be used in which there is onecommon active time applicable for all aggregated serving cells.

In some embodiments, RRC controls DRX operation by configuring thefollowing parameters: 1) drx-onDurationTimer: the duration at thebeginning of a DRX Cycle; 2) drx-SlotOffset: the delay before startingthe drx-onDurationTimer; 3) drx-InactivityTimer: the duration after thePDCCH occasion in which a PDCCH indicates a new UL or DL transmissionfor the MAC entity; 4) drx-RetransmissionTimerDL (per DL HARQ processexcept for the broadcast process): the maximum duration until a DLretransmission is received; 5) drx-RetransmissionTimerUL (per UL HARQprocess): the maximum duration until a grant for UL retransmission isreceived; 6) drx-LongCycleStartOffset: the Long DRX cycle anddrx-StartOffset which defines the subframe where the Long and Short DRXCycle starts; 7) drx-ShortCycle (optional): the Short DRX cycle; 8)drx-ShortCycleTimer (optional): the duration the UE shall follow theShort DRX cycle; 9) drx-HARQ-RTT-TimerDL (per DL HARQ process except forthe broadcast process): the minimum duration before a DL assignment forHARQ retransmission is expected by the MAC entity; and/or 10)drx-HARQ-RTT-TimerUL (per UL HARQ process): the minimum duration beforea UL HARQ retransmission grant is expected by the MAC entity.

In various embodiments, if a DRX cycle is configured, an active time mayinclude a time while: 1) a drx-onDurationTimer, a drx-InactivityTimer, adrx-RetransmissionTimerDL, a drx-RetransmissionTimerUL, or anra-ContentionResolutionTimer is running; 2) a scheduling request is senton PUCCH and is pending; or 3) a PDCCH indicating a new transmissionaddressed to the C-RNTI of the MAC entity has not been received aftersuccessful reception of a random access response for a random accesspreamble not selected by the MAC entity among contention-based randomaccess preambles.

In some embodiments, operation of DRX gives a UE an opportunity todeactivate radio circuits to save power. In such embodiments, whetherthe UE actually remains in a non-active time during the DRX period maybe decided by the UE. For example, the UE may perform inter-frequencymeasurements that cannot be conducted during an on duration, and thusmay be performed some other time.

In certain embodiments, parameterization of a DRX cycle may involve atrade-off between battery saving and latency. In various embodiments, along DRX period may be beneficial for a UE's battery life. In someembodiments, it may be beneficial to monitor downlink control signalingin each slot (or more frequently) to receive uplink and downlink grantsand/or to react to changes in traffic characteristics.

In various embodiments, if DRX is configured, periodic SRS,semi-persistent SRS, CSI on PUCCH, and semi-persistent CSI on PUSCH mayonly be sent by a UE during an active-time. In such embodiments, RRC mayfurther restrict CSI on PUCCH so that they are only sent during anon-duration (e.g., referred to as CSI masking).

In some embodiments, DRX-related timers (e.g., drx-InactivityTimer,drx-RetransmissionTimerDL and drx-ShortCycleTimer) may be started andstopped by events such as reception of a PDCCH grant or a MAC controlelement (e.g., DRX command MAC CE, long DRX command MAC CE). In suchembodiments, a DRX status (e.g., active time or non-active time) of a UEmay change from one slot and/or symbol to another slot and/or symboland, therefore, may not always be predictable by the UE or a gNB. Incertain embodiments, because a UE may need some time to process receiveddownlink control signaling or information changing a DRX status, and mayrequires some time to prepare a CSI and/or SRS report (e.g., thisprocessing time may depend on an implementation of the UE), somerelaxation of CSI and/or SRS reporting during DRX may be used, such asin NR.

In certain embodiments, assuming that a UE is currently in an activetime and a drx-InactivityTimer is running, if the UE receives in a lastslot and/or symbol before a DRX inactivity timer expires (e.g., slot N)a PDCCH indicating a new transmission (e.g., UL or DL), the UE may alsobe in an active time in the next slot and/or symbol (e.g., slot N+1).Due to processing time in the UE, the UE may only know at the end ofslot N or beginning of slot N+1, that slot N+1 is still in the activetime. In such embodiments, assuming that a periodic CSI report isconfigured to be transmitted in slot N+1, the UE may not have time toprepare a CSI report for transmission, since it may be assumed to enterDRX (e.g., be in non-active time during slot N+1). As may beappreciated, the UE might not be able to transmit a periodic CSI reportin slot N+1.

In various embodiments, to relax UE requirements for CSI and/or SRSreporting during DRX and to introduce some predictable UE behavior thatavoids a need of gNB double decoding (e.g., decoding assuming CSI and/orSRS as well as no CSI and/or SRS transmission), the following may beperformed: 1) in a current symbol n, if a MAC entity would not be in anactive time considering grants, assignments, a DRX command MAC CE, along DRX command MAC CE received, and a scheduling request sent until 4ms prior to symbol n if evaluating all DRX active time conditions asspecified in this clause: a) not transmit periodic SRS andsemi-persistent SRS; and b) not report CSI on PUCCH and semi-persistentCSI on PUSCH; and 2) if CSI masking (e.g., csi-Mask) is setup by upperlayers: a) in current symbol n, if drx-onDurationTimer would not berunning considering grants, assignments, a DRX command MAC CE, and along DRX command MAC CE received until 4 ms prior to symbol n ifevaluating all DRX Active Time conditions as specified in this clause:not report CSI on PUCCH.

In various embodiments, a UE determines whether to report CSI and/or SRSin a current symbol n by considering downlink signaling (e.g., grants,assignments, a DRX command MAC CE, a long DRX command MAC CE) and/or SRtransmissions impacting DRX status having been received respectivelytransmitted until 4 ms prior to this symbol n. If the symbol n would notbe in active time according to a downlink signaling received respectiveto SR sent until 4 ms prior to symbol n if evaluating all DRX activetime conditions, the UE does not transmit periodic SRS and/or CSI onPUCCH and/or semi-persistent CSI on PUSCH.

In some embodiments, with the introduction of WUS signal, starting adrx-onDurationTimer may not be a deterministic event. In variousembodiments, a drx-onDurationTimer may be started according to aconfigured DRX cycle. In certain embodiments, the starting of adrx-onDurationTimer depends on whether WUS signaling at a PDCCH-WUSoccasion indicates for a UE to wake-up to monitor PDCCH during a nextoccurrence of a drx-onDuration (e.g., indicating for a UE to start thedrx-onDurationTimer at its next occasion). In various embodiments,because an offset between a WUS occasion and a next occurrence ofOnDuration (e.g., also referred to as WUS-Offset) may be shorter than 4ms, but the condition for determining whether to report CSI and/or SRSin a symbol n depends on control signaling received until 4 ms beforesymbol n, it may not be clear how and whether the WUS-related signaling(e.g., PDCCH-WUS) affects the CSI and/or SRS reporting during DRX.

As used herein, the term eNB and/or gNB may be used to refer to a basestation, but may be replaceable by any other radio access node (e.g.,BS, eNB, gNB, AP, NR, and so forth). Furthermore, while the methodsdescribed herein may be mainly in the context of 5G NR, various methodsdescribed herein may be equally applicable to other mobile communicationsystems supporting power saving mechanisms. It should further be notedthat, as used herein, the term “onDuration” period may refer to a timeperiod at the beginning of a DRX cycle in which the drx-onDurationTimeris running, as one embodiment is shown in FIG. 4 .

Specifically, FIG. 4 is a timing diagram illustrating one embodiment ofa DRX cycle 400. The DRX cycle 400 includes a first WUS occasion 402 anda first onDuration 404 over a time 406. A first WUS offset 408 is a timebetween the first WUS occasion 402 and the first onDuration 404. Thefirst onDuration 404 has a time duration 410. As may be appreciated, allof the onDurations in the DRX cycle 400 may have the same time duration410. Further, the DRX cycle 400 also includes a second WUS occasion 412and a second onDuration 414 over the time 406. A second WUS offset 416is a time between the second WUS occasion 412 and the second onDuration414. Moreover, the DRX cycle 400 also includes a third WUS occasion 418and a third onDuration 420 over the time 406. A third WUS offset 422 isa time between the third WUS occasion 418 and the third onDuration 420.

In a first embodiment, a UE may not consider WUS (e.g., PDCCH-WUS, orwake-up PDCCH) for determining whether to report CSI and/or SRS. In suchan embodiment, the UE doesn't consider WUS-related signaling todetermine whether a symbol n would be in a DRX active time and/or not bein the active time and whether to transmit periodic SRS, transmitsemi-persistent SRS, report CSI on PUCCH, and/or report semi-persistentCSI on PUSCH. In one implementation of the first embodiment, the UE may,for the purpose of CSI and/or SRS reporting, assume that a timer (e.g.,drx-onDurationTimer) is started according to a configured DRX cycle. Insuch an implementation, the UE may transmit periodic SRS,semi-persistent SRS, CSI on PUCCH, and/or semi-persistent CSI on PUSCHeven if the timer (e.g., drx-onDurationTimer) is not running and the UEis not in active time (e.g., WUS signal hasn't indicated for the UE tostart the timer—drx-onDurationTimer). A first example of animplementation of the first embodiment is found herein. In the firstexample WUS-PDCCH denotes a WUS signal (e.g., PDCCH-based power savingsignal and/or channel) indicating whether a UE is to start a timer(e.g., drx-onDurationTimer) at a beginning of a next DRX cycle (e.g.,next onDuration). The first example of the implementation of the firstembodiment is as follows: 1) in current symbol n, if the MAC entitywould not be in active time considering grants, assignments, a DRXcommand MAC CE, a long DRX command MAC CE (e.g., excluding PDCCH-WUS)received, and/or a scheduling request sent until 4 ms prior to thesymbol n if evaluating all DRX active time conditions as specified inthis clause: a) not transmit periodic SRS and semi-persistent SRS; and2) not report CSI on PUCCH and semi-persistent CSI on PUSCH; and 2) ifCSI masking (e.g., csi-Mask) is setup by upper layers: in current symboln, if drx-onDurationTimer would not be running considering grants,assignments, a DRX command MAC CE, and/or a long DRX command MAC CE(e.g., excluding PDCCH-WUS) received until 4 ms prior to symbol n ifevaluating all DRX active time conditions as specified in this clause:not report CSI on PUCCH.

In another implementation of the first embodiment, the UE doesn'tconsider WUS-related signaling to determine whether a symbol n would bein a DRX active time and/or not be in an active time and whether totransmit periodic SRS, transmit semi-persistent SRS, report CSI onPUCCH, and/or report semi-persistent CSI on PUSCH for the first X ms ofeach onDuration. In such an embodiment, during this first X ms the UEreports CSI and/or SRS regardless of the DRX status of the UE (i.e.,regardless of whether a drx-onDurationTimer is actually running—such asif PDCCH-WUS has indicated to the UE to start and/or not to start thedrx-onDurationTimer). In this embodiment, the UE may considerWUS-related signaling (e.g., PDCCH-WUS) only after the first X ms of theonDuration. According to certain implementations of the firstembodiment, X may be equal to 4 ms minus a configured WUS-Offset if theWUS-Offset (e.g., WUS occasion for monitoring PDCCH-WUS is configuredWUS-Offset before the start of the onDuration) is smaller than 4 ms. IfWUS-Offset is larger or equal to 4 ms, X is equal to zero.

In a second embodiment, a UE considers “Wake-Up” signals (e.g.,PDCCH-WUS) for determining whether to report CSI and/or SRS. In such anembodiment, the UE considers WUS-related signaling to determine whethera symbol n would be in DRX active time and/or not be in active time andwhether to transmit periodic SRS, transmit semi-persistent SRS, reportCSI on PUCCH, and/or report semi-persistent CSI on PUSCH. In such anembodiment, the UE may not transmit periodic SRS, not transmitsemi-persistent SRS, not report CSI on PUCCH, and/or not reportsemi-persistent CSI on PUSCH during (e.g., the beginning of) onDurationeven if drx-onDurationTimer is running and UE is in active time (e.g.,WUS signal has indicated the UE to start drx-onDurationTimer) if theWUS-Offset is smaller than 4 ms. This may be because if the WUS occasionis configured to be less than 4 ms before the start of a next DRX cycle,the UE cannot consider the PDCCH-WUS signaling for determining whetherto send CSI and/or SRS for the first (e.g., 4−WUS-Offset) ms of theOnDuration period (e.g., the UE would act as not having received aPDCCH-WUS indicating for the UE to start the drx-onDurationTimer.

A second example of the second embodiment is shown herein. In theexample of the second embodiment, WUS-PDCCH denotes a WUS signal (e.g.,PDCCH-based power saving signal and/or channel) indicating whether theUE should start a drx-onDurationTimer at the beginning of a next DRXcycle (e.g., next onDuration). The second example of the secondembodiment is as follows: 1) in current symbol n, if a MAC entity wouldnot be in an active time considering grants, assignments, a DRX commandMAC CE, a long DRX command MAC CE, a PDCCH-WUS received, and/or ascheduling request sent until 4 ms prior to symbol n if evaluating allDRX active time conditions as specified in this clause: a) not transmitperiodic SRS and semi-persistent SRS; and b) not report CSI on PUCCH andsemi-persistent CSI on PUSCH; and 2) if CSI masking (e.g., csi-Mask) issetup by upper layers: in current symbol n, if drx-onDurationTimer wouldnot be running considering grants, assignments, a DRX command MAC CE, along DRX Command MAC CE, and/or a PDCCH-WUS received until 4 ms prior tosymbol n if evaluating all DRX active time conditions as specified inthis clause: not report CSI on PUCCH.

In a third embodiment, a UE may report CSI and/or SRS during an“onDuration period” at a beginning of a DRX cycle even though thedrx-onDurationTimer is not running (e.g., the UE is not in active time)if a WUS occasion is configured with an offset before a start of theonDuration which is less than X ms. If the WUS occasion is configuredwith an offset before the start of the onDuration which is equal to orlarger than X ms, the UE considers the WUS related signaling (e.g.,WUS-PDCCH) for determining whether the UE reports CSI and/or SRS. In onespecific implementation of the third embodiment, X is equal to 4 ms.According to another implementation of the third embodiment, if theoffset (e.g., offset between a WUS occasion and an OnDuration) is equalto or larger than 4 ms in a current symbol n, and if the MAC entitywould not be in an active time considering WUS-signaling, grants,assignments, a DRX command MAC CE, a long DRX command MAC CE received,and/or a scheduling request sent until 4 ms prior to symbol n ifevaluating all DRX active time conditions, the UE doesn't transmitperiodic SRS, does not transmit semi-persistent SRS, does not report CSIon PUCCH, and/or does not report semi-persistent CSI on PUSCH. If theoffset is smaller than 4 ms, in current symbol n, and if the MAC entitywould not be in active time considering grants, assignments, a DRXcommand MAC CE, a long DRX command MAC CE (e.g., excludingWUS-signaling) received, and/or scheduling request sent until 4 ms priorto symbol n if evaluating all DRX active time conditions, the UE doesn'ttransmit periodic SRS, does not transmit semi-persistent SRS, doesn'treport CSI on PUCCH, and/or does not report semi-persistent CSI onPUSCH. By not considering WUS-signaling for determining whether the UEis in an active time in symbol n, the UE may report CSI and/or SRS ifdrx-onDurationTimer is not running (e.g., WUS signaling indicates to notstart the drx-onDurationTimer at the beginning of the next DRX cycle).

A third example of the third embodiment is shown herein. In the exampleof the third embodiment, WUS-PDCCH denotes a WUS signal (e.g.,PDCCH-based power saving signal and/or channel) indicating whether theUE should start a drx-onDurationTimer at the beginning of a next DRXcycle. The third example of the third embodiment is as follows: 1) ifWUS-offset is smaller than 4 ms, in current symbol n, if the MAC entitywould not be in active time considering grants, assignments, a DRXcommand MAC CE, a long DRX command MAC CE (e.g., excluding PDCCH-WUS)received, and/or a scheduling request sent until 4 ms prior to symbol nif evaluating all DRX active time conditions as specified in thisclause: a) not transmit periodic SRS and semi-persistent SRS defined;and b) not report CSI on PUCCH and semi-persistent CSI on PUSCH; 2)else, in current symbol n, if the MAC entity would not be in active timeconsidering PDCCH-WUS, grants, assignments, a DRX command MAC CE, a longDRX command MAC CE received, and/or scheduling request sent until 4 msprior to symbol n if evaluating all DRX active time conditions asspecified in this clause: a) not transmit periodic SRS andsemi-persistent SRS; and b) not report CSI on PUCCH and semi-persistentCSI on PUSCH; 3) if CSI masking (e.g., csi-Mask) is setup by upperlayers and if WUS-offset is smaller than 4 ms in current symbol n, ifdrx-onDurationTimer would not be running considering grants,assignments, a DRX command MAC CE, and/or a long DRX command MAC CE(e.g., excluding PDCCH-WUS) received until 4 ms prior to symbol n ifevaluating all DRX active time conditions as specified in this clause:a) not report CSI on PUCCH; 4) else in current symbol n, ifdrx-onDurationTimer would not be running considering PDCCH-WUS, grants,assignments, a DRX command MAC CE, and/or a long DRX command MAC CEreceived until 4 ms prior to symbol n if evaluating all DRX active timeconditions as specified in this clause: not report CSI on PUCCH.

In a fourth embodiment, a UE is configured with a configurationindicating whether to report CSI and/or SRS (e.g., periodic SRS,semi-persistent SRS and/or report CSI on PUCCH and semi-persistent CSIon PUSCH) for the first x ms of OnDuration regardless of a DRX status ofthe UE (e.g., regardless of whether drx-onDurationTimer is actuallyrunning or not—PDCCH-WUS has indicated that the UE is to start and/ornot start the drx-onDurationTimer) if WUS-Offset is smaller than x ms,e.g. 4 ms, or indicating not to report CSI and/or SRS for the first X msof onDuration if WUS-Offset is smaller than x ms. The fourth embodimentmay be combined with other WUS related configurations (e.g.,WUS-Offset). According to one implementation of the fourth embodiment,the UE may receive a configuration via RRC signaling.

According to one implementation of the fourth embodiment, the PDCCH-WUS(e.g., wake-up PDCCH) may indicate to the UE whether to transmitperiodic SRS, transmit semi-persistent SRS, report CSI on PUCCH, and/orreport semi-persistent CSI on PUSCH for the first x ms of OnDuration ifWUS-Offset is smaller than 4 ms. In such an embodiment, X may be equalto a 4 ms WUS-Offset.

In a fifth embodiment, a UE may start or restart a timer (e.g.,bwp-InactivityTimer) upon reception of a PDCCH-WUS (e.g., wake-up PDCCH)indicating for the UE to switch a current active BWP. The PDCCH-WUS maycontain a BWP-ID field indicating to the UE which BWP to monitor PDCCHfor the next onDuration so that the UE will have already switched to aBWP appropriate for expected traffic by the time the onDuration starts.According to one implementation of the fifth embodiment, the UE maystart and/or restart the timer upon having received a PDCCH-WUSindicating for the UE to switch to a different DL BWP (e.g., compared toa current active (DL) BWP associated with a serving cell) for a nextonDuration. According to another implementation of the fifth embodiment,the UE starts and/or restarts a timer (e.g., a bwp-InactivityTimer)associated with an active DL BWP upon having received a PDCCH-WUSindicating to the UE to switch to a different DL BWP (e.g., compared toa current active (DL) BWP associated with a serving cell) for a nextonDuration if the timer is started.

In a sixth embodiment, a UE stops a timer (e.g., a bwp-InactivityTimer)associated with an active DL BWP of a serving cell if the UE monitors aPDCCH-WUS at a WUS-occasions. In such an embodiment, the UE mayimplicitly activate a “wake-up” specific BWP for monitoring a wake-upPDCCH at WUS occasions. The UE may switch autonomously from a currentactive DL BWP to a wake-up BWP for PDCCH-WUS monitoring. In certainembodiments, a situation in which the timer expires and the UE has toswitch to a DefaultDownlinkBWP or initialDownlinkBWP may be avoided.

FIG. 5 is a flow chart diagram illustrating one embodiment of a method500 for reporting transmission for discontinuous reception. In someembodiments, the method 500 is performed by an apparatus, such as theremote unit 102. In certain embodiments, the method 500 may be performedby a processor executing program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

In various embodiments, the method 500 includes determining 502 whethera symbol occurs within a discontinuous reception on duration timeperiod. In some embodiments, the method 500 includes, in response todetermining that the symbol occurs within the discontinuous reception onduration time period, determining 504 whether to transmit a report. Incertain embodiments, the method 500 includes transmitting 506 the reportregardless of whether a discontinuous reception on duration timer isrunning.

In certain embodiments, the method 500 further comprises not consideringwake up signaling to determine whether the discontinuous reception onduration timer is started. In some embodiments, the discontinuousreception on duration time period comprises a duration of thediscontinuous reception on duration timer. In various embodiments, thereport is a channel state information report.

In one embodiment, the report is a periodic channel state informationreport. In certain embodiments, the report is a semi-persistent channelstate information report. In some embodiments, the report is a soundingreference signal report.

In various embodiments, the report is a periodic sounding referencesignal report. In one embodiment, the report is a semi-persistentsounding reference signal report. In certain embodiments, the report istransmitted on a physical uplink control channel.

In some embodiments, the report is transmitted on a physical uplinkshared channel. In various embodiments, the report is transmitted duringa predetermined time period of the discontinuous reception on durationtime period. In one embodiment, the predetermined time period comprisesa beginning number of milliseconds of the discontinuous reception onduration time period.

In one embodiment, a method comprises: determining whether a symboloccurs within a discontinuous reception on duration time period; inresponse to determining that the symbol occurs within the discontinuousreception on duration time period, determining whether to transmit areport; and transmitting the report regardless of whether adiscontinuous reception on duration timer is running.

In certain embodiments, the method further comprises not consideringwake up signaling to determine whether the discontinuous reception onduration timer is started.

In some embodiments, the discontinuous reception on duration time periodcomprises a duration of the discontinuous reception on duration timer.

In various embodiments, the report is a channel state informationreport.

In one embodiment, the report is a periodic channel state informationreport.

In certain embodiments, the report is a semi-persistent channel stateinformation report.

In some embodiments, the report is a sounding reference signal report.

In various embodiments, the report is a periodic sounding referencesignal report.

In one embodiment, the report is a semi-persistent sounding referencesignal report.

In certain embodiments, the report is transmitted on a physical uplinkcontrol channel.

In some embodiments, the report is transmitted on a physical uplinkshared channel.

In various embodiments, the report is transmitted during a predeterminedtime period of the discontinuous reception on duration time period.

In one embodiment, the predetermined time period comprises a beginningnumber of milliseconds of the discontinuous reception on duration timeperiod.

In one embodiment, an apparatus comprises: a processor that: determineswhether a symbol occurs within a discontinuous reception on durationtime period; and, in response to determining that the symbol occurswithin the discontinuous reception on duration time period, determineswhether to transmit a report; and a transmitter that transmits thereport regardless of whether a discontinuous reception on duration timeris running.

In certain embodiments, the processor does not consider wake upsignaling to determine whether the discontinuous reception on durationtimer is started.

In some embodiments, the discontinuous reception on duration time periodcomprises a duration of the discontinuous reception on duration timer.

In various embodiments, the report is a channel state informationreport.

In one embodiment, the report is a periodic channel state informationreport.

In certain embodiments, the report is a semi-persistent channel stateinformation report.

In some embodiments, the report is a sounding reference signal report.

In various embodiments, the report is a periodic sounding referencesignal report.

In one embodiment, the report is a semi-persistent sounding referencesignal report.

In certain embodiments, the report is transmitted on a physical uplinkcontrol channel.

In some embodiments, the report is transmitted on a physical uplinkshared channel.

In various embodiments, the report is transmitted during a predeterminedtime period of the discontinuous reception on duration time period.

In one embodiment, the predetermined time period comprises a beginningnumber of milliseconds of the discontinuous reception on duration timeperiod.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

The invention claimed is:
 1. A method comprising: determining whether asymbol occurs within a predetermined time period from a start of an onduration time period; in response to determining that the symbol occurswithin the predetermined time period from the start of the on durationtime period, determining whether to transmit a report; receivinginformation indicating whether to not start a discontinuous reception onduration timer, wherein the information is received an offset timeperiod prior to the on duration time period; in response to theinformation indicating to not start the discontinuous reception onduration timer, not starting the discontinuous reception on durationtimer; and transmitting the report even though the discontinuousreception on duration timer is not running as a result of determiningthat the symbol occurs within the predetermined time period from thestart of the on duration time period.
 2. The method of claim 1, furthercomprising not considering wake up signaling to determine whether thediscontinuous reception on duration timer is started.
 3. The method ofclaim 1, wherein the on duration time period comprises a duration of thediscontinuous reception on duration timer.
 4. The method of claim 1,wherein the report is a periodic channel state information report. 5.The method of claim 1, wherein the report is a semi-persistent channelstate information report.
 6. The method of claim 1, wherein the reportis a sounding reference signal report.
 7. The method of claim 1, whereinthe report is a periodic sounding reference signal report.
 8. The methodof claim 1, wherein the report is a semi-persistent sounding referencesignal report.
 9. The method of claim 1, wherein the report istransmitted on a physical uplink control channel.
 10. The method ofclaim 1, wherein the report is transmitted on a physical uplink sharedchannel.
 11. The method of claim 1, wherein the report is transmittedduring the predetermined time period of the on duration time period. 12.The method of claim 11, wherein the predetermined time period comprisesa beginning number of milliseconds of the on duration time period. 13.An apparatus comprising: a processor that: determines whether a symboloccurs within a predetermined time period from a start of an on durationtime period; in response to determining that the symbol occurs withinthe predetermined time period from the start of the on duration timeperiod, determines whether to transmit a report; not starting adiscontinuous reception on duration timer in response to receivinginformation indicating to not start the discontinuous reception onduration timer, wherein the information is received an offset timeperiod prior to the on duration time period; and a transmitter thattransmits the report even though the discontinuous reception on durationtimer is not running as a result of determining that the symbol occurswithin the predetermined time period from the start of the on durationtime period.
 14. The apparatus of claim 13, wherein the processor doesnot consider wake up signaling to determine whether the discontinuousreception on duration timer is started.
 15. The apparatus of claim 13,wherein on duration time period comprises a duration of thediscontinuous reception on duration timer.
 16. The apparatus of claim13, wherein the report is a periodic channel state information report.17. The apparatus of claim 13, wherein the report is a semi-persistentchannel state information report.
 18. The apparatus of claim 13, whereinthe report is a sounding reference signal report.